home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 22
/
Cream of the Crop 22.iso
/
bbs
/
hstdoor2.zip
/
MMENU10F.ZIP
/
HELP.TXT
< prev
next >
Wrap
Text File
|
1995-07-03
|
5KB
|
121 lines
*** Troubleshooting the MultiMenu Door by Mike Robinson ***
MultiMenu writes error conditions to file ERROR.LOG in the current
directory. Check this file. If it says that MultiMenu cannot find or
read a certain file, check your MMENU.CFG file or batch file to
locate where this file is specified. Change the path to the file, or
relocate the file. Check the spelling of the path and filename
carefully. A single misplaced character will cause an error. Verify
that the directories and files specified actually do exist.
Check that the list of doors in MMENU.CFG begins with the command
word BEGIN and ends with the command word END. If you leave out the
END command, then all the commands after that point will be ignored.
This can cause all sorts of problems.
------------------------------------------------------------------------------
*** PROBLEM: MultiMenu works on local end but the caller sees nothing.
This is caused by a failure to open the com port. The wrong port is
being used, the port is non-standard, or there is a conflict with
other hardware or software. MultiMenu determines the port number to
use by reading the door drop file:
DOOR.SYS com port number is on line number 1
DORINFOx.DEF com port number is on line number 4
SFFILE.DAT com port number is on line number 6
In the batch file that runs MultiMenu, the first parameter on the
command line should be the full path and file name of one of these
files. Check the door drop file to be sure that the correct com port
number is specified on the indicated file line. You can also force it
to use a certain port by using the PORT command in MMENU.CFG. This
will override the port specified in the door drop file.
If MultiMenu starts, shows some of the initial displays, and then
seems to halt, this is almost always an IRQ conflict with another
device or software on the system. The most common such problem is an
internal modem and IO card trying to use the same IRQ number. Make
sure that nothing else on your system is using the IRQ and IO base
address used by MultiMenu. Other devices which could cause conflicts
are a mouse, sound card, CD-ROM card, network card, tape backup card,
scanner card, or just about any other piece of "extra" hardware
plugged into the computer.
MultiMenu uses the "standard" IBM PC clone com port settings which are:
COM1 IRQ 4 $03F8
COM2 IRQ 3 $02F8
COM3 IRQ 4 $03E8
COM4 IRQ 3 $02E8
If your com port does not use these settings, then it is called
non-standard. Which means that MultiMenu does not know the correct
settings, so you must "tell" MultiMenu which settings to use. The
commands to do this are:
Port 2
IRQ 3
IO $02F8
Put these commands in MMENU.CFG. The settings shown above are for a
standard COM2. You will have to adjust these to match the settings
used on your com port. Note the $ in front of number in the IO
command. This $ indicates that it is a hexadecimal number (base16).
Also note that if you use a "true blue" IBM PS/2 made by IBM then
MultiMenu detects the PS/2 and uses slightly different settings for
COM3 and COM4 only.
------------------------------------------------------------------------------
*** PROBLEM: MultiMenu runs a door, but then MultiMenu does not
restart and the caller is returned to the BBS.
In MMENU.CFG check that there is a GOTO LOOP command after the
commands that run the door. The GOTO LOOP command causes the batch
file to return back to the :LOOP statement at the beginning of
MENU.BAT and will restart MultiMenu
If you run any batch files inside of MENU.BAT then you should use a
DOS CALL command to run the batch file like this:
:DOOR1
CALL DOOR1.BAT
GOTO LOOP
If you do not use the DOS CALL command, then the batch file will run
once, but it will not return back to MENU.BAT. If you do not run any
batch files in MENU.BAT then the DOS CALL command is not required.
------------------------------------------------------------------------------
*** PROBLEM: I registered MultiMenu, but it is not writing a log file
of the caller's activities in the door.
Reasons why log may not be written:
1. Program running in local mode. Log not written in local mode.
2. Program not registered.
3. Log OFF command used.
4. LogName command is spelled wrong.
5. LogName command is preceded by a semicolon or it is not all the
way up against the left margin of MMENU.CFG.
6. The directory specified for the log is spelled wrong and/or
does not exist.
7. The name of the log file is spelled wrong and/or it is not a
legal DOS file name.
8. Some other program is deleting the log. Spitfire and TriBBS use
a temporary log for each node. After a caller logs off, the
temporary log is copied to the main log. The temporary log is
then deleted.